Fix typo in test name and strengthen the assertion

Two tweaks:

• Typo: graphphs → graphqls (both function name and snapshot key)
• Optional: sanity-check that the file actually changed after formatting

Apply this diff within the shown range:

-#[test]
-fn can_format_graphphs_files() {
+#[test]
+fn can_format_graphqls_files() {
     let fs = MemoryFileSystem::default();
     let mut console = BufferConsole::default();

     let file_path = Utf8Path::new("file.graphqls");
     fs.insert(file_path.into(), SPACING_GRAPHQLS_SANITY_BEFORE.as_bytes());

     let (fs, result) = run_cli(
         fs,
         &mut console,
         Args::from(["format", "--write", file_path.as_str()].as_slice()),
     );

     assert!(result.is_ok(), "run_cli returned {result:?}");
+
+    // Sanity: ensure the formatter changed the file
+    let mut content = String::new();
+    fs.open(file_path).unwrap().read_to_string(&mut content).unwrap();
+    assert_ne!(
+        content,
+        SPACING_GRAPHQLS_SANITY_BEFORE,
+        "expected the GraphQL schema to be reformatted"
+    );

     assert_cli_snapshot(SnapshotPayload::new(
         module_path!(),
-        "can_format_graphphs_files",
+        "can_format_graphqls_files",
         fs,
         console,
         result,
     ));
 }

If there are any other lingering “graphphs” typos in the repo, a quick scan helps:

🏁 Script executed:

#!/bin/bash
# Find any misspellings of "graphphs" across the repo
rg -n --no-ignore-vcs --hidden 'graphphs'

Length of output: 205

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Sanity-check: is "graphqls" a widely used languageId?

Many editors/tools only emit "graphql" as the languageId. Accepting "graphqls" is harmless, but let’s confirm it’s used in the wild and ensure tests cover it.

Run this script to check where "graphqls" is referenced in the repo (tests, config, docs):

And, to confirm whether VS Code or LSP conventions include "graphqls" as a languageId, please run this web query:

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo 'Occurrences of "graphqls" across the repo:'
rg -n --pretty --hidden --glob '!.git' '"graphqls"'

echo
echo 'Callers/tests for try_from_language_id/try_from_extension:'
rg -n --pretty --hidden --glob '!.git' 'try_from_language_id|try_from_extension'

Length of output: 4527

🌐 Web query:

Does VS Code or common GraphQL extensions define "graphqls" as a language identifier (languageId), or is "graphql" the de-facto standard?

💡 Result:

The de-facto standard language identifier (languageId) for GraphQL in VS Code and its common extensions is "graphql". Neither VS Code core nor major GraphQL extensions define "graphqls" as a language identifier; "graphql" is used for both query documents and schema files.

Supporting details:

• The official [VS Code language identifiers documentation][8] only mentions "graphql" as a recognized language mode; "graphqls" is not documented as a languageId.

• The most popular and canonical GraphQL extensions—including GraphQL for VSCode[7], Apollo's editor extension[6], and vscode-graphql by GraphQL Foundation[2][5]—all use "graphql" as the languageId for syntax highlighting, autocompletion, and language server features.

• File associations in the extensions typically map both .graphql and .gql files (and sometimes .graphqls) to the "graphql" languageId[2][4][5]. The naming "graphqls" as an extension for schema files (.graphqls) is a file extension convention in some codebases but does not imply a separate languageId.

• For example, the [vscode-graphql extension documentation][2][5] only references "graphql" as the language identifier—and "graphql" is the value used internally for language features, regardless of whether the file is a schema or a query.

• Some developers use .graphqls as a filename extension for GraphQL schema files, but this is a convention at the file system level and does not affect the languageId, which remains "graphql"[2][4].

Summary table:

Conclusion:
Use "graphql" as the languageId for both GraphQL queries and schemas in VS Code and common extensions. The identifier "graphqls" is not registered as a languageId; it's only seen occasionally as a filename extension convention[2][5][8].

Citations:

• 1: https://community.apollographql.com/t/vs-code-extension-not-working-with-graphql-code-gen/5628
• 2: https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql
• 3: https://graphql.org/learn/schema/
• 4: https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql-syntax
• 5: https://github.com/graphql/vscode-graphql
• 6: https://www.apollographql.com/docs/ide-support/vs-code
• 7: https://marketplace.visualstudio.com/items?itemName=kumar-harsh.graphql-for-vscode
• 8: https://code.visualstudio.com/docs/languages/identifiers